Skip to content

chore(deps): update tunit to 1.67.0 - #6793

Merged
thomhurst merged 1 commit into
mainfrom
renovate/tunit
Sep 12, 2026
Merged

thomhurst merged 1 commit into
mainfrom
renovate/tunit

Conversation

@thomhurst

@thomhurst thomhurst commented Sep 12, 2026

Copy link
Copy Markdown
Owner

This PR contains the following updates:

Package Type Update Change
TUnit nuget minor 1.66.271.67.0
TUnit.AspNetCore nuget minor 1.66.271.67.0
TUnit.Assertions nuget minor 1.66.271.67.0
TUnit.Assertions.FSharp nuget minor 1.66.271.67.0
TUnit.Core nuget minor 1.66.271.67.0
TUnit.Engine nuget minor 1.66.271.67.0

Release Notes

thomhurst/TUnit (TUnit)

v1.67.0: 1.67.0

What's Changed
Other Changes
Dependencies
New Contributors

Full Changelog: v1.66.27...v1.67.0


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@thomhurst thomhurst added dependencies Pull requests that update a dependency file MINOR renovate-bot labels Sep 12, 2026
@thomhurst
thomhurst enabled auto-merge (squash) September 12, 2026 12:17
@thomhurst
thomhurst deployed to Pull Requests September 12, 2026 12:17 — with GitHub Actions Active
@thomhurst
thomhurst deployed to Pull Requests September 12, 2026 12:17 — with GitHub Actions Active
@thomhurst
thomhurst deployed to Pull Requests September 12, 2026 12:17 — with GitHub Actions Active
@chatgpt-codex-connector

chatgpt-codex-connector Bot commented Sep 12, 2026

Copy link
Copy Markdown

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review Status Commit Review trigger
📝 Code Review Completed 2026-09-12T12:19:52.318907Z 654d8db PR opened
ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

@coderabbitai

coderabbitai Bot commented Sep 12, 2026

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 447099f4-9a5e-40f9-9c2f-e2aabc7a239a

📥 Commits

Reviewing files that changed from the base of the PR and between 6993dd2 and 654d8db.

📒 Files selected for processing (1)
  • Directory.Packages.props

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.


📝 Walkthrough

Walkthrough

The central package management file updates six TUnit-related packages from version 1.66.27 to 1.67.0. Verify package versions remain unchanged.

Changes

TUnit package version update

Layer / File(s) Summary
Update TUnit package versions
Directory.Packages.props
The versions for TUnit, TUnit.AspNetCore, TUnit.Core, TUnit.Engine, TUnit.Assertions, and TUnit.Assertions.FSharp change from 1.66.27 to 1.67.0.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~5 minutes

Change: Other

Suggested reviewers: mvanhorn

Merge Risk: ⚪ Minimal · up to 654d8

The package-only update is narrowly scoped and introduces no identified merge-blocking risk.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: updating TUnit dependencies from 1.66.27 to 1.67.0.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch renovate/tunit

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

A rabbit checks the package row
Six TUnit hops now forward go
Verify rests in place
New versions set the pace
The props file wears a brighter glow

Comment @coderabbitai help to get the list of available commands.

@greptile-apps

greptile-apps Bot commented Sep 12, 2026

Copy link
Copy Markdown

Greptile Summary

This PR updates the centrally managed TUnit package family from 1.66.27 to 1.67.0.

  • Keeps TUnit, TUnit.Core, TUnit.Engine, TUnit.Assertions, TUnit.Assertions.FSharp, and TUnit.AspNetCore on the same version.
  • Requires no corresponding package-lock or restore-configuration updates.

Confidence Score: 5/5

The coordinated dependency update appears safe to merge.

No actionable failure was identified; the related TUnit packages remain version-aligned, and no checked-in lock or restore constraints require further changes.

Important Files Changed

Filename Overview
Directory.Packages.props Coherently updates all six centrally pinned TUnit packages to version 1.67.0 without introducing a concrete compatibility issue.

Reviews (1): Last reviewed commit: "chore(deps): update tunit to 1.67.0" | Re-trigger Greptile

This was referenced Sep 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file MINOR renovate-bot

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants